home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20000217-20000824
/
000012_news@columbia.edu _Thu Feb 17 23:10:05 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2000-08-23
|
2KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id XAA27550
for <kermit.misc@watsun.cc.columbia.edu>; Thu, 17 Feb 2000 23:10:05 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id XAA13260
for kermit.misc@watsun.cc.columbia.edu; Thu, 17 Feb 2000 23:09:05 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: jrd@cc.usu.edu (Joe Doupnik)
Subject: Re: TELNET error with K95 1.19
Message-ID: <3ERmaxlQV+sL@cc.usu.edu>
Date: 17 Feb 00 20:34:22 MDT
Organization: Utah State University
To: kermit.misc@columbia.edu
In article <88id1n$ae2$1@news.value.net>, Mark Sapiro <msapiro@value.net> writes:
> Bob Rodriguez <robertr@netcom17.netcom.com> wrote:
> : The new TELNET terminal negotiation options in version 1.19
> : seems to have introduced a problem when telneting to special ports
> : that are not Unix logins. There's a MUD that I was able to get to ok with
> : 1.17 as candum.acc.umu.se 2001, but now it times out with the following errors:
>
> <snip>
>
> The short answer here is don't use the TELNET command if the
> port doesn't speak telnet; use SET HOST instead.
>
> For more info, see the thread "Help with telnet in C-Kermit 7"
> from about a week ago in this newsgroup (you can look it up
> at www.deja.com if it's gone from your news server).
>
> --
> Mark Sapiro <msapiro@value.net> The highway is for gamblers,
> San Francisco Bay Area, California better use your sense - B. Dylan
--------
Yup, that's the short answer. There could have been another approach
to the difficulty which is a client offers Telnet Options but does not halt
waiting for responses. In principle, it says in bold quotes, Options can
occur at any time in the session, though the principle collides with what
to do about text exchanged in the meanwhile. Isn't that correct Jeff?
If it were correct then a regular Telnet client could offer Options and
still make progress on non-Telnet servers. I wish my UnixWare Telnet were
that way, but it isn't. This boils down to chickens, eggs, and should we
wait to check for traffic before crossing the road, or some such muddle.
Joe D.